Skip to content

Add _GNU_SOURCE definition unconditionally #14651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

petk
Copy link
Member

@petk petk commented Jun 24, 2024

Since Autoconf >= 2.70 the _GNU_SOURCE and some other extensions are defined unconditionally regardless whether the __EXTENSIONS__ can be safely defined. Some obsolete Solaris systems once had issues with compiling a default set of standard system headers when __EXTENSIONS__ was defined. Autoconf 2.69 and earlier checked based on that and defined the _GNU_SOURCE conditionally. This condition is not relevant on current systems anymore.

Since Autoconf >= 2.70 the _GNU_SOURCE and some other extensions are
defined unconditionally regardless whether the __EXTENSIONS__ can be
safely defined. Some obsolete Solaris systems once had issues with
compiling a default set of standard system headers when __EXTENSIONS__
was defined. Autoconf 2.69 and earlier checked based on that and defined
the _GNU_SOURCE conditionally. This condition is not relevant on current
systems anymore.
@petk petk merged commit 909d331 into php:master Jun 25, 2024
9 of 11 checks passed
@petk petk deleted the patch-safe-to-define-extensions branch June 25, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants